Data migrating method taking end time into consideration

ABSTRACT

A data migrating method including calculating, in a case where data stored in a volume is migrated to another volume, a required period of time for migrating the data based on a size of data to be migrated and volume configuration information on the volume in which the migrated data is stored and the volume to which the data is to be migrated, determining a start time at which the data migration starts to generate a volume migration plan, setting a priority of the generated volume migration plan, prioritizing, in a case where a periods of time during which the generated volume migration plan is executed and a period of time during which an existing volume migration plan is executed are overlapped with each other, and changing the start time of at least one of those volume migration plans having a lower priority.

CROSS-REFERENCED TO RELATED APPLICATIONS

The present application is a continuation of application Ser. No.12/871,961, filed Aug. 31, 2010; which is a continuation of applicationSer. No. 11/968,236, filed Jan. 2, 2008, now U.S. Pat. No. 7,809,905;which claims priority from Japanese patent application JP 2007-036179filed on Feb. 16, 2007, the content of which is hereby incorporated byreference into this application.

BACKGROUND OF THE INVENTION

This invention relates to a computer system including a storage systemfor storing data of a large volume, and more particularly to a techniquefor migrating data stored in the storage system.

Description of the Related Art

Recently, a volume of data processed by a computer system in a company,a local government, a public office, or a financial institution isincreasing year by year. Under the circumstances, a new storage system(storage device) is added, or data is migrated from an existing storagesystem to another existing storage system, as a countermeasure againstan increase in the volume of data.

Also, the computer system is complicated in configuration when aplurality of storage systems are added with an increase in volume ofdata to be managed. As a technique for solving the above-mentionedproblem, there has been proposed a technique of virtualization ofcomputer systems. The virtualization of computer systems means atechnique of virtualizing a plurality of storage systems that areconnected to each other on a network by logically recognizing them asone computer system. Because operation management can be centralized byvirtualizing the computer system, it is possible to reduce managementcosts.

Also, with the application of the virtualization technique of computersystems, the volumes (logical or physical storage areas serving as unitsof data storage) of the computer systems can be classified into aplurality of storage tiers on the basis of characteristics such asperformance or type. For example, in a technique disclosed in JP2005-196625 A, access frequency of data stored in each volume isregularly monitored to realize an appropriate arrangement of storagesystems according to function characteristics corresponding to theaccess frequency.

SUMMARY OF THE INVENTION

However, in the technique disclosed in JP 2005-196625 A, in a case wherea plurality of processes are required to be executed at the same time,the priority order of the respective processes is not considered. Forthat reason, in a case where a certain migrating process is executed,even when a migrating process whose deadline approaches is to beexecuted, it is impossible to execute a new migrating process until themigrating process in execution has been completed. Accordingly, there isa fear that the new migrating process cannot be executed by itsdeadline, and it causes a problem.

This invention has been made in view of the above-mentioned problems,and therefore it is an object of this invention to give a priority toeach migrating process and reschedule on the basis of the priority tocomplete the execution of the data migration by the deadline in the casewhere a plurality of migrating process requests are executed.

A representative aspect of this invention is as follows. That is, thereis provided a computer system, comprising: a storage system; a hostcomputer that is coupled to the storage system via a network; and astorage management server that can access to the storage system and thehost computer, wherein the storage system comprises a first interfacethat is coupled to the network, a first processor that is coupled to thefirst interface, a first memory that is coupled to the first processor,and a storage device that stores data that is read or written by thehost computer, and provides at least one storage area of the storagedevice for the host computer as at least one volume, wherein the storagemanagement server comprises a second interface that is coupled to thestorage system, a second processor that is coupled to the secondinterface, and a second memory that is coupled to the second processor,wherein the second memory stores configuration information of thevolume, and

wherein the second processor executes a volume migrating process formigrating data stored in the volume to another volume, in which thesecond processor: calculates a required period of time for migrating thedata based on a size of data to be migrated, volume configurationinformation of a first volume in which the data to be migrated isstored, and volume configuration information of a second volume that isa volume to which the data is migrated; generate a volume migration planby determining a start time at which the data migration starts based onthe calculated required period of time and an input end time; sets apriority of the generated volume migration plan; and changes, in a casewhere a period of time during which the produced volume migration planis executed and a period of time during which an existing volumemigration plan is executed are overlapped with each other, based on aresult of comparing a priority of the generated volume migration planwith a priority of the existing volume migration plan, the start time ofat least one of the generated volume migration plan and the existingvolume migration plan, in accordance with the priority of the volumemigration plan which has a higher priority of the generated volumemigration plan and the existing volume migration plan.

According to this embodiment of this invention, execution of a volumemigrating process higher in priority is started prior to execution of avolume migrating process lower in priority, thereby enabling themigrating process of the volume higher in priority to be completed byits designated time.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention can be appreciated by the description which infollows in conjunction with the following figures, wherein:

FIG. 1 is a diagram showing an example of a hardware configuration of acomputer system according to an embodiment of this invention;

FIG. 2 is a diagram showing an example of the configuration of a storagesystem according to the embodiment of this invention;

FIG. 3 is a diagram showing an example of the hardware configuration ofa virtualization device according to the embodiment of this invention;

FIG. 4 is a diagram showing an example of the configuration of a storagemanagement server according to the embodiment of this invention;

FIG. 5 is a diagram showing an example of the data configuration of astorage volume table according to the embodiment of this invention;

FIG. 6 is a diagram showing an example of an external volume tableaccording to the embodiment of this invention;

FIG. 7 is a diagram showing an example of a storage table according tothe embodiment of this invention;

FIG. 8 is a diagram showing an example of a migration group tableaccording to the embodiment of this invention;

FIG. 9 is a diagram showing an example of a migration plan tableaccording to the embodiment of this invention;

FIG. 10 is a diagram showing an example of a storage tier tableaccording to the embodiment of this invention;

FIG. 11 is a diagram showing an example of a volume table according tothe embodiment of this invention;

FIG. 12 is a diagram showing an example of a volume relation tableaccording to the embodiment of this invention;

FIG. 13 is a diagram showing an example of a priority table according tothe embodiment of this invention;

FIG. 14 is a flowchart showing an example of a procedure of in producingthe storage tier according to the embodiment of this invention;

FIG. 15 is a screen for registering a storage tier according to theembodiment of this invention;

FIG. 16 is a flowchart showing an example of a procedure of determininga tier order of the storage tier table according to the embodiment ofthis invention;

FIG. 17 is a flowchart showing an example of a procedure of producing amigration plan according to the embodiment of this invention;

FIG. 18 is a flowchart showing an example of a procedure of producing amigration plan according to the embodiment of this invention;

FIG. 19 shows a screen for registering the migration plan according tothe embodiment of this invention;

FIG. 20 is a diagram for explaining a specific example of a procedure ofproducing the migration plan according to the embodiment of thisinvention;

FIG. 21 is a flowchart showing a procedure of a volume migrating processregistered in the migration plan according to the embodiment of thisinvention;

FIG. 22 is an example of a flowchart that instructs a stop of a datamigrating process of the storage system according to the embodiment ofthis invention; and

FIG. 23 is a diagram for explaining a specific example of a procedure ofexecuting a migration plan according to the embodiment of thisinvention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Now, a description will be given of an embodiment of this invention withreference to the accompanying drawings.

First, a description will be given of a specific configuration of acomputer system 100 according to the embodiment of this invention withreference to FIG. 1 to FIG. 4.

FIG. 1 is a diagram showing an example of a hardware configuration ofthe computer system 100 according to the embodiment of this invention.

The computer system 100 includes one or more storage systems 101, astorage management server 102, a management client 103, one or more hostcomputers 104, storage networks 105, a management network 106, and avirtualization device 107.

Each of the host computers 104 executes various business processings(for example, a database process, a web application process, and astreaming process) by using storage resources that are supplied by thestorage systems 101 and the virtualization device 107. Each of the hostcomputers 104 is formed of, for example, a workstation system, a mainframe computer, or a personal computer. Each of the host computers 104is connected to the plurality of storage systems 101 via thevirtualization device 107, to thereby recognize the storage resourcesthat are supplied by the respective storage systems 101 as one storageresource logically.

The virtualization device 107 is formed of, for example, avirtualization switch, an intelligent switch, or a virtualizationdedicated device. The virtualization device 107 may be formed of astorage system that provides a virtualization function.

Each of the storage systems 101 has one or more controllers 111 and aplurality of storage devices 112.

Each of the controllers 111 controls the plurality of storage devices112 as a redundant arrays of inexpensive disks (RAID) configurationcorresponding to RAID levels (for example, 0, 1 and 5). In the RAIDconfiguration, the plurality of storage devices 112 are managed as oneRAID group. The RAID group is configured by grouping four or eightstorage devices 112 as one set. In other words, the storage areas thatare supplied io by the respective storage devices 112 are assembled toconfigure one RAID group. In the RAID group, one or more logical volumesserving as access units from the host computer 104 are defined.

Each of the storage devices 112 is a physical device that actuallystores data therein. More specifically, the physical device may be afibre channel (FC) disk drive, a serial advanced technology attachment(SATA) disk drive, a parallel advanced technology attachment (PATA) diskdrive, a serial attached SCSI (SAS) disk drive, a fibre attachedtechnology adapted (FATA) disk drive, or a small computer systeminterface (SCSI) disk drive. As the storage device 112, a semiconductormemory such as a flash memory can be employed together.

The management network 106 is connected to the one or more hostcomputers 104, the one or more storage systems 101, the virtualizationdevice 107, the storage management server 102, and the management client103, so as to be used for transmitting or receiving managementinformation.

The management client 103 is a computer for maintaining and managing thecomputer system 100. A user inputs a command for storage management viaa web browser 131 that is installed in the management client 103, tothereby maintain and manage the computer system 100. The command forstorage management may be, for example, a command for increasing ordecreasing the number of storage devices 112, a command for instructinga change in RAID configuration, or a command for setting communicationpaths between the host computers 104 and the storage systems 101.

The storage management server 102 receives various commands for storagemanagement from the management client 103, and maintains and manages thecomputer system 100. The storage management server 102 has a datamigration management program 121. The data migration management program121 executes a process for migrating the volumes between the storagetiers. The data migration management program 121 is a generic term ofthe respective programs for migrating the volumes, and will be describedin detail with reference to FIG. 4. Also, the storage management server102 has a storage device 122 for storing information such as theconfiguration information of the computer system 100.

FIG. 2 is a diagram showing an example of the configuration of thestorage system 101 according to the embodiment of this invention. Thestorage system 101 includes the controller 111 and the storage device112.

The controller 111 includes a host interface (I/F) 211, a managementinterface (I/F) 212, a processor 213, a cache 214, and a memory 215.

The host interface 211 is a network interface for connecting to the hostcomputers 104 through the storage network 105.

The management interface 212 is a network interface for connecting tothe storage management servers 102 and the management client 103 throughthe management network 106.

The processor 213 receives a data input/output request from the hostcomputer 104, and controls the input and output of data with respect tothe storage device 112. The processor 213 is, for example, a centralprocessing unit (CPU). The cache 214 temporarily stores the data that isinput to or output from the storage device 112.

The memory 215 stores information necessary for various controlmicroprograms and processes. The memory 215 stores a volume migrationprogram 231, a table management program 232, an I/O control program 233,a data deletion program 234, and a storage volume table 241 therein.

The volume migration program 231 is a program for changing acorrespondence between the volumes and the storage device 112. The hostcomputer 104 identifies the volumes by using identifiers (ID). Also, thehost io computer 104 recognizes the logical position of the storage area(logical address) on the volume from/to which data is read/written, butdoes not recognize the physical position of the storage area (physicaladdress) of the storage device 112. The volume migration means to changethe logical position of the storage area on the volume which isrecognized by the host computer 104. The volume migration program 231migrates a volume that belongs to a certain storage tier (describedlater with reference to FIG. 10) to another storage tier.

The table management program 232 is a program for reading informationthat is stored in the storage volume table 241 or writing informationthat is to be stored therein.

The I/O control program 233 is a program for controlling data input toor output from the storage device 112 in response to an I/O request fromthe host computer 104.

The data deletion program 234 is a program for deleting the data storedin the storage device 112. The deletion of data is a process forpreventing the contents of the storage device in which the data has beenstored from being read by writing data (for example, data represented by“1” and “0” placed at random, data represented by merely “0”, and datarepresented by merely “1”) in the physical area of the storage device112 in which the data has been stored, once or a plurality of times.

The storage volume table 241 stores information indicative of acorrespondence between the volumes and the storage device 112, andinformation related to the volume characteristics therein. The detailsof the storage volume table will be described with reference to FIG. 5.

FIG. 3 is a diagram showing an example of the hardware configuration ofthe virtualization device 107 according to the embodiment of thisinvention.

The virtualization device 107 includes a host interface (I/F) 311, astorage interface (I/F) 314, a processor 315, a memory 316, a cache 313,a storage device 112, and a management interface (I/F) 312. It isunnecessary that the storage device 112 be installed in thevirtualization device 107.

The host interface 311 is a network interface for connecting to the hostcomputers 104 through the storage network 105.

The storage interface 314 is a network interface for connecting to thestorage system 101 through the storage network 105. The number ofstorage interfaces 314 is one in FIG. 3, but it is desirable that thestorage interface 314 be disposed in each of the storage systems 101.

The processor 315 executes the program stored in the memory 316, tothereby execute a process of virtualizing the storage resources (storagedevices 112) that are supplied by the respective storage systems 101 bylogically recognizing them as one storage resource.

The memory 316 stores information necessary for various controlmicroprograms and processes therein. The memory 316 stores a storagevolume table 241, an external volume table 341 (volume information), avolume migration program 231, a table management program 232, an I/Ocontrol program 233, a data deletion program 234, and an externalassociation control program 331 therein.

The virtualization device 107 has one or more virtual volumes 321. Eachof the virtual volumes 321 is a volume to which the volume that issupplied by the storage system 101 is virtually allocated. Hereinafter,the volume that is supplied by the storage system 101 is called“external volume”. The address space (an area where the address ismapped) of the virtual volume 321 is mapped in the address space of theexternal volume.

The host computer 104 recognizes the virtual volume 321 as the storagearea of the storage system 101, and issues an I/O request with respectto the virtual volume 321. Upon receiving the I/O request from the hostcomputer 104, the virtualization device 107 executes address conversionbetween the virtual volume 321 and the external volume. Then, thevirtualization device 107 transfers the I/O request from the hostcomputer 104 to the storage system 101, and accesses to the externalvolume. The respective external volumes that are supplied by theplurality of storage systems 101 are allocated to the virtual volumes321. In this way, the virtualization device 107 virtualizes the storageresources of the plurality of storage systems 101 by logicallyrecognizing them as one storage resource.

The external association control program 331 is a program forcontrolling an external association between the virtualization device107 and the storage system 101. More specifically, the externalassociation control program 331 executes an address conversion betweenthe virtual volume 321 and the external volume and a command transfer tothe storage system 101.

The external volume table 341 stores information indicative of thecorrespondence between the virtual volume 321 and the external volumetherein. The details of the external volume table 341 will be describedwith reference to FIG. 6.

The cache 313 temporarily stores data that is input to or output fromthe storage device 112 and the virtual volume 321 therein.

The management interface 312 is a network interface for connecting tothe storage management server 102 and the management client 103 throughthe management network 106.

FIG. 4 is a diagram showing an example of the configuration of thestorage management server 102 according to the embodiment of thisinvention.

The storage management server 102 includes an interface (I/F) 411, amonitor 412, a processor 413, an input device 414, a memory 415, and thestorage device 122.

The interface 411 is a network interface for connecting to themanagement network 106. More specifically, the interface 411 can beformed of a LAN adapter. The storage management server 102 acquires thevolume configuration information of the storage device 112 from thestorage system 101 through the interface 411, and transmits aninstruction of the volume migration to the storage system 101.

The monitor 412 is a display device for supplying a screen for storagemanagement to a user under graphical user interface (GUI) environments.The input device 414 is a device for inputting a storage managementcommand such as a keyboard or a mouse. The monitor 412 and the inputdevice 414 may not be disposed in the storage management server 102.

The processor 413 executes the program stored in the memory 415 tomaintain and manage the computer system 100. In addition, the processor413 executes the data migration management program 121 to execute aprocess of migrating the volumes between the storage tiers.

The memory 415 stores the data migration management program 121 therein.Specifically, the data migration management program 121 includes astorage operation program 431, a priority management program 432, a GUIprogram 433, a table management program 434, an execution managementprogram 435, and a configuration information acquisition program 436.

The storage operation program 431 is a program for instructing theexecution of the data migrating process and the data deleting process tothe storage system 101 and the virtualization device 107. An object towhich the data migrating process is to be instructed is as follows.

The processor 413 instructs the data migration to the storage system 101to which the migration source volume and the migration destinationvolume belong in the case where the migration source volume and themigration destination volume belong to the same storage system 101.Also, the processor 413 may instruct the data migration to thevirtualization device 107 in the case where the migration source volumeand the migration destination volume belong to the same storage system101, and are connected to the virtualization device 107.

In addition, in the case where the migration source volume and themigration destination volume belong to the different storage systems101, the processor 413 instructs the data migration to thevirtualization device 107. Also, in the case where the migration sourcevolume or the migration destination volume belongs to the virtualizationdevice 107, the processor 413 instructs the data migration to thevirtualization device 107.

On the other hand, the processor 413 executes the storage operationprogram 431, to thereby instruct the execution of the data deletingprocess to the virtualization device 107 or the storage system 101 towhich the migration source volume belongs.

The priority management program 432 is a program for determining thepriority of the data migrating process.

The GUI program 433 is a program that displays the information on thestorage system 101 and the virtualization device 107 on the monitor 412,and provides an interface to be used for operating the storagemanagement server 102 to an administrator. The details of the interfacethat is displayed on the monitor 412 by the GUI program 433 will bedescribed with reference to FIG. 15 and FIG. 19. The GUI may be replacedwith another interface such as a command line interface.

The table management program 434 is a program that manages a storagetable 441 that is stored in the storage device 122, a migration grouptable 442, a migration plan table 443, a storage tier table 444, avolume table 445, a volume relation table 446, and a priority table 447.

The execution management program 435 is a program that instructs theexecution or stop of the migration plan that is configured by the volumemigrating process and the data deleting process.

The configuration information acquisition program 436 is a program thatacquires the configuration information on the storage system 101, thevirtualization device 107, and the host computer 104 through themanagement network 106.

Also, the storage device 122 stores the storage table 441 (physicalconfiguration information), the migration group table 442 (migrationgroup information), the migration plan table 443 (migration planinformation), the storage tier table 444, the volume table 445 (physicalconfiguration information), the volume relation table 446, and thepriority table 447. The details of those tables will be described withreference to FIG. 7 to FIG. 13.

FIG. 5 is a diagram showing an example of the data configuration of thestorage volume table 241 according to the embodiment of this invention.The storage volume table 241 stores information necessary for reading orwriting the data in the volumes by using the controller 111 therein.

The storage volume table 241 includes a VOL #511, a VDEV #512, a RAIDlevel 513, a disk type 514, and a capacity 515. The storage volume table241 produces a record in each of the volumes.

The VOL #511 is No. for identifying the volumes within the storagesystem 101. The VDEV #512 is No. for identifying the virtual device towhich the storage area on the volume is allocated.

The RAID level 513 is a RAID level of the storage area on the volume.The RAID level 513 may include the drive configuration of the storagedevice 112. The disk type 514 is a disk type of the storage devices 112that provide the storage areas on the volumes. The capacity 515 is astorage capacity of the corresponding volume.

FIG. 6 is a diagram showing an example of the external volume table 341according to the embodiment of this invention. The external volume table341 stores information necessary for virtualizing the respective storageresources (storage devices 112) provided by the plurality of storagesystems 101 by logically recognizing them as one storage resource.

The external volume table 341 associates the VOL #611, the external Port#612, the IP address 613, and the external VOL #614 with each other. Inthe external volume table 341, a record is produced in each of theproduced virtual volumes 321.

The VOL #611 is an identifier for identifying the virtual volume 321that has been produced in the virtualization device 107.

The external Port #612 is No. for identifying a port (an externalassociation port of the virtualization device 107) for transferring theI/O request with respect to the virtual volume 321 to the externalvolume from the host computer 104.

The IP address 613 represents the IP address of the storage system 101having the external volume. The IP address 613 is used for identifyingthe storage system 101 having the external volume. The information foridentifying the storage system 101 having the external volume can beconfigured by world wide name (WWN).

The external VOL #614 is No. for identifying the external volume withinthe storage system 101. The external VOL #614 corresponds to the VOL#511 of the storage volume table 241.

FIG. 7 is a diagram showing an example of the storage table 441according to the embodiment of this invention. The storage table 441stores information related to the storage system 101 therein.

The storage table 441 includes a storage system ID 711, a storage name712, and a device type 713. In the storage table 441, a record isproduced in each of the storage systems 101.

The storage system ID 711 is an identifier for identifying the storagesystem 101. The storage name 712 is a name of the storage system.

The device type 713 is the type of storage system 101. The device type713 stores, for example, a model number of the device therein.

FIG. 8 is a diagram showing an example of the migration group table 423according to the embodiment of this invention. The migration group table423 stores information related to the migration group therein.

The volume migration is executed in the group unit that is called“migration group” collectively. When the administrator executes thevolume migrating process, the administrator first produces the migrationgroup, and registers the produced migration group in the migration grouptable 423. Thereafter, the administrator adds the volume that migratesthe volume (hereinafter referred to as “migration source volume”) to themigration group.

Subsequently, the administrator selects the storage tier (hereinafterreferred to as “migration destination storage tier”) to which the volumeis migrated with respect to the produced migration group. In addition,the administrator selects the volume that belongs to the selectedstorage tier as the migration destination volume (hereinafter referredto as “migration destination volume”) in the respective migration sourcevolumes.

The migration group table 423 includes an MG ID 811, a belonging VOL#812, a migration destination tier 813, and a migration destination tier814. In the migration group table 423, the record is produced in each ofthe migration groups.

The MG ID 811 is an identifier for identifying the migration group. Thebelonging VOL #812 is an identifier of the volume added to the migrationgroup.

The migration destination tier 813 represents information on the storagetier to which the respective volumes of the migration group belong. Thestorage tier will be described with reference to FIG. 10.

The migration destination tier 814 is an identifier of the storage tierin which the volume that belongs to the migration group is migrated bythe migration of the volume. The symbol “-” of the migration destinationstorage tier 814 indicates that the migration destination storage tieris not designated.

FIG. 9 is a diagram showing an example of the migration plan table 443according to the embodiment of this invention. The migration plan table443 stores information related to the volume migrating process in eachof the migration groups therein.

The volume migration is executed according to the migration plan in eachof the migration groups. The administrator designates the migrationdestination storage tier and the time at which the migration should becompleted in the migration group to execute the volume migration.

The migration plan table 443 includes an MG ID 911, a priority 912, ascheduled start time 913, a scheduled end time 914, and a designated endtime 915. In the migration table 443, the record is produced in each ofthe migration plans.

The MG ID 911 is an identifier for identifying the migration group. TheMG ID 911 corresponds to the MG ID 811 of the migration group table 442.

The priority 912 stores the priorities of the respective migrationplans. The priority is determined by the data migration managementprogram 121 according to the information on the migration source tier ofthe migration group, the migration destination tier, and the prioritytable 447. The priority may be changed by the administrator.

The scheduled start time 913 is a scheduled time at which the migrationplan starts to be executed. The processor 413 of the storage managementserver 102 executes the data migration management program 121, tothereby calculate a required period of time for the data migration onthe basis of the configuration information of the migration plan anddetermine the scheduled start time according to the required period oftime and the scheduled end time 914.

The scheduled end time 914 is a scheduled time at which the execution ofthe migration plan is completed. The scheduled end time 914 isdetermined on the basis of the priority 912 and the designated end time915 with the execution of the data migration management program 121. Thescheduled start time and the scheduled end time may be changed on thebasis of the priority of another migration plan when the anothermigration plan is registered.

The scheduled end time 915 is a time at which the execution of themigration plan is to be completed. The administrator designates thedesignated end time at the time of producing the migration plan.

An execution status 916 stores the execution status of the migrationplan therein. In the execution status 916 there are stored, for example,“unprocessed”, “migrating”, “deleting”, “suspended”, “completed”, and“failed”.

“Unprocessed” represents that the migration is not yet processed.“Migrating” represents that the volume that belongs to the migrationplan is being migrated. “Deleting” represents that the migration of thevolume that belongs to the migration plan has been completed, and thedata of the migration destination volume is being deleted.

“Suspended” represents that the subject migration group is suspended bythe data migration management program 121 in order to migrate anothermigration group in advance. “Completed” indicates that the migration ofthe respective volumes of the migration group are migrated, and thedeletion of the respective migration source volumes have been completed.“Failed” represents that the data migrating process or the data deletingprocess of the migration group fails.

FIG. 10 is a diagram showing an example of the storage tier table 444according to the embodiment of this invention. The storage tier table444 stores information related to the storage tier therein. The storagetier means the classification of the volumes which is determined on thebasis of the characteristics such as the performance and the type.

The storage tier table 444 includes a storage tier ID 1011, a tier name1012, a tier order 1013, and a tier condition. The tier conditionincludes a capacity 1014, a device ID 1015, a device type 1016, a RAIDlevel 1017, and a disk type 1018. In the storage tier table 444, therecord is produced in each of the storage tiers.

The storage tier ID 1011 is an identifier for identifying the storagetier. The tier name 1012 is a name of the storage tier.

The tier order 1013 is a relative order of the performance of thestorage tier. The tier order 1013 is set on the basis of the tiercondition when the administrator produces the storage tier. Theproduction of the storage tier will be described with reference to FIG.16. In addition, the data migration management program 121 is executed,to thereby set the priority in the priority table 447 on the basis ofthe tier order 1013. This will be described with reference to FIG. 14.

The tier condition is a condition for specifying the storage tier towhich the volume belongs. As described above, the tier conditionincludes the capacity 1014, the device ID 1015, the device type 1016,the RAID level 1017, and the disk type 1018.

Also, the tier condition other than the device type 1016 may be thecombination of two or more of those conditions. An item in which thetier condition is not designated is represented by the symbol “-”.

The capacity 1014 is a storage capacity necessary to belong to thestorage tier. The device ID 1015 is an identifier for identifying thestorage system 101. The device type 1016 is a type of the storage system101. The RAID level 1017 is a RAID level of the storage tier.

The disk type 1018 is a disk type of the storage device 112 thatprovides the storage area of the storage tier. For example, the disktype of “FC” represents an FC disk. Also, the disk type of “SATA”represents an SATA disk.

FIG. 11 is a diagram showing an example of the volume table 445according to the embodiment of this invention. The volume table 445stores the information related to the volume that is supplied by thestorage system 101.

The volume table 445 includes a volume ID 1111, an MG ID 1112, a storageID 1113, a VOL #1114, a RAID level 1115, a disk type 1116, and acapacity 1117. In the volume table 445, a record is produced in each ofthe volumes.

The volume ID 1111 is an identifier for identifying the volume in thestorage system 101 by the host computer 104. The MG ID 1112 is anidentifier for identifying the migration group serving as a unit ofoperating the migrations of the volumes collectively.

The storage ID 1113 is an identifier for identifying the storage system101. The VOL #1114 is No. for identifying the volume within the storagesystem 101. The RAID level 1115 is a RAID level of the volume.

The disk type 1116 is the disk type of the storage device 112 whichsupplies the storage area of the volume. The disk type 1116 is, forexample, information for distinguishing the FC disk and the SATA diskfrom each other. More specifically, the disk type of “FC” indicates theFC disk. Also, the disk type of “SATA” indicates the SATA disk. Thecapacity 1117 is a storage area of the volume.

FIG. 12 is a diagram showing an example of the volume relation table 446according to the embodiment of this invention. The volume relation table446 stores the information related to the progress of the data migratingprocess of the volume that belongs to the migration group therein.

The volume relation table 446 includes an MG ID 1211, a migration sourcevolume ID 1212, a migration destination volume ID 1213, a capacity 1214,and a progress 1215. In the volume relation table 446, a record isproduced in each of the volumes that belong to the migration group.

The MG ID 1211 is an identifier for identifying the migration group towhich the migration source volume belongs. The migration source volumeID 1212 is an identifier for identifying the volume that belongs to themigration group. The migration source volume ID 1212 corresponds to thevolume ID 1111 of the volume table 445.

The migration destination volume ID 1213 is an identifier foridentifying the volume to which the data of the migration source volumeis migrated. The migration destination volume ID 1213 corresponds to thevolume ID 1111 of the volume table 445. The capacity 1214 is thecapacity of the migration source volume.

The progress 1215 represents the execution status of the volumemigration and the date deletion of the migration source volume. Theprogress 1215 stores, for example, “unprocessed”, “migrating”,“migration completed”, “deleting”, “interrupted”, and “completed”.

“Unprocessed” indicates that the migration of the subject volume is notprocessed. “Migrating” means that the subject volume is being migrated.“Migration completed” represents that the migration of the subjectvolume has been completed.

“Deleting” indicates that the migration of the subject volume has beencompleted, and the data of the migration source volume is being deleted.“Interrupted” indicates a state in which the migration of the subjectvolume or the data deletion of the migration source volume is suspended.

“Completed” indicates that the migration of the subject volume and thedeletion of the migration source volume have been completed. In thissituation, the data of the migration source volume may not deleted afterthe migration of the volume. In this case, the status of “deleting” isnot set, and “completed” is set at the time when the migration of thevolume is completed.

FIG. 13 is a diagram showing an example of the priority table 447according to the embodiment of this invention. The priority table 447stores the priority that is used to determine a process to beprioritized and the condition for allocating the subject priority in thecase where the execution timings of the data migrating processes areoverlapped with each other, therein.

The priority table 447 includes the condition #1311, a migrationcondition 1312, a priority 1313, and a condition order 1314. In thepriority table 447, a record is produced in each of the conditions(hereinafter referred to as “migration condition”) for determining thepriority of the data migration. Also, the priority table 447 has acondition that is held as an initial value, and a condition that isproduced by the data migration management program 121 when theadministrator produces the storage tier. Also, the administrator mayregister data in the priority table 447.

The condition #1311 is an identifier for identifying the migrationcondition.

The migration condition 1312 stores the contents of the migrationcondition therein. The migration condition has a condition that is heldas an initial value, and a condition that is produced on the basis ofthe storage tier table according to the data migration managementprogram 121.

In the migration condition 1312, there is a case in which the capacityof the migration destination storage tier is set as the condition as ina case of a condition #1 “the capacity of the migration source storagetier is 25% or lower at the time of migration”. Also, there is a case inwhich the processing content is set as the condition as in a case of acondition #8 “complete deletion of data in the migration source VOL”.Further, there is a case in which the data migration from the migrationsource storage tier to the migration destination storage tier is set asthe condition as in a case of a condition #2 “the data migration fromTier2 to Tier1”. Each of Tier1, Tier2, and Tier3 of FIG. 13 is a name ofstorage tier.

The priority 1313 indicates the priority of the data migrating processon the basis of the migration condition. The data migration is scheduledon the basis of the priority 1313 of the migration plan by executing thedata migration management program 121.

The priority 1313 is determined, for example, on the basis of thefollowing rules. The rule is managed by the data migration managementprogram 121. The condition based on the capacity at the time ofmigration such as the condition #1 is set to the highest priority, andthe condition #8 is set to the lowest priority. The lower the numericvalue, the higher the priority. Under the condition that is determinedaccording to the migration source storage tier and migration destinationstorage tier such as the conditions #2 to #7, the priority is higher inthe case where the tier order of the migration destination storage tieris higher than the tier order of the migration source storage tier.Further, in the case where the tier order of the migration destinationstorage tier is highest, the priority is higher. In this case, thepriority of the condition in which the tier order of the migrationsource storage tier is higher is higher.

On the other hand, in the case where the tier order of the migrationdestination storage tier is lower than the tier order of the migrationsource storage tier, the priority of the condition in which the tierorder of the migration source storage tier is higher is higher. In thecase where the tier order of the migration source storage tier is equalto each other, the priority of the condition in which the tier order ofthe migration destination storage tier is higher is higher.

When the data deleting process is defined separately, as in the case ofthe condition #8, it is possible to give the priority to the datamigrating process and the data deleting process, individually.

When the tier order of the storage tier is set to Tier1, Tier2, andTier3 in a descending order, the conditions are determined on the basisof the above-mentioned rules as shown in the condition #1 to thecondition #8 of FIG. 13.

The condition order 1314 is an order at the time of applying themigration condition. The condition order 1314 is determined by executingthe data migration management program 121. For example, in the casewhere the condition #1 and the condition #2 are satisfied at the sametime, that is, in the case where there occurs a status in which thecapacity of the Tier2 is equal to or lower than 25% at the time ofmigrating data from Tier2 to Tier1, the condition #1 that is lower inthe value of the condition order is prioritized, and “1” is set in thepriority 1313.

FIG. 14 is a flowchart showing an example of a procedure of producingthe storage tier according to the embodiment of this invention. Thisprocessing is appropriately executed by the administrator in the storagemanagement server 102.

First, the processor 413 of the storage management server 102 executesthe table management program 434, to thereby acquire the configurationinformation of the storage system 101 from the storage table 441 and thevolume table 445. In addition, the processor 413 executes the GUIprogram 433, to thereby display the configuration information of thestorage device through the web browser 131 of the management client 103(Step 1411).

Subsequently, the administrator refers to the information that isdisplayed through the process of Step S1411, produces the storage tier,and registers the produced storage tier in the storage tier table 444(Step 1412). Hereinafter, a description will be given of a procedure ofproducing the storage tier with reference to FIG. 15 showing a screenthat is displayed by executing the GUI program 433 in order to producethe storage tier.

FIG. 15 is a screen for registering the storage tier according to theembodiment of this invention.

The administrator first inputs a tier name to a field of the tier name2111. The administrator then sets the configuration contents in a searchcondition 2112 on the screen by selecting each content from pull-down,to thereby set the tier condition of the storage tier. Finally, theadministrator operates an execute button 2113 in order to register theselected contents. Also, in the case where the administrator does notregister the set contents, the manager operates a cancel button 2114 inorder to cancel the selected contents.

The information that has been input from the management client 103 istransmitted to the storage management server 102 by operating theexecute button 2113. Upon receiving the information that has been inputfrom the management client 103, the processor 413 of the storagemanagement server 102 executes the table management program 434, tothereby register the produced storage tier in the storage tier table444.

Then, the processor 413 of the storage management server 102 executesthe execution management program 435 to search the storage tier table444 and determine whether another storage tier exists, or not (Step1413). In the case where another storage tier does not exist (the resultin Step 1413 is “no”), processing is completed directly.

On the other hand, in the case where another storage tier exists in thestorage tier table 444 (the result in Step 1413 is “yes”), the processor413 of the storage management server 102 executes the prioritymanagement program 432 to compare the received storage tier with thetier condition in each of other storage tiers, and determine the tierorder (Step 1414). The procedure of determining the tier order will bedescribed with reference to FIG. 16.

The processor 413 of the storage management server 102 executes thepriority management program 432, to thereby produce the priority table447 on the basis of the tier order that is determined in Step 1414 (Step1415).

FIG. 16 is a flowchart showing an example of a procedure of determiningthe tier order 1013 of the storage tier table 444 according to theembodiment of this invention.

The processor 413 of the storage management server 102 first executesthe execution management program 435, to thereby compare the tiercondition of the storage tier that has been produced by the process inStep 1412 with the tier condition of the storage tier that has beenregistered in the storage tier table 444, and determine whether thedevice type coincides with each other, or not (Step 2011).

In the case where the device type is different from each other (theresult in Step 2011 is “no”), the processor 413 of the storagemanagement server 102 sets the storage tier having the higher-orderdevice type to be higher (Step 2013). The higher-order device type meansthe higher-performance storage system. The storage performance isdetermined according to the I/O speed of data, the system configuration,and the like. The information for determining which of higher order orlower order the device type is may be held in the storage managementserver 102 in advance, or may be determined by the administrator.

In the case where the device type coincides with each other (the resultin Step 2011 is “yes”), the processor 413 of the storage managementserver 102 executes the execution management program 435, to therebycompare the disk type of the storage tier produced in the process ofStep 1412 with the disk type of the tier condition of the storage tierregistered in the storage tier table 444, and determine whether the disktype is equal to each other or not. Alternatively, it is determined thatthe disk type is not set to at least one of those (Step 2012).

In the case where the device type is different from each other (theresult in Step 2012 is “no”), the processor 413 of the storagemanagement server 102 sets the storage tier having the higher-order disktype set to be higher (Step 2015). The higher-order disk type indicatesthe higher performance disk type. The performance of the disk type isdetermined according to the I/O speed of data, the lifetime of the disk,and the like. The information for determining which of higher order orlower order the disk type is may be held in the storage managementserver 102 in advance, or may be determined by the administrator.

In the case where the device type coincides with each other or is notset to at least one of those (the result in Step 2012 is “yes”), theprocessor 413 of the storage management server 102 executes theexecution management program 435, to thereby compare the RAID level ofthe storage tier produced in the process of Step 1412 with the RAIDlevel of the tier condition of the storage tier registered in thestorage tier table 444, and determine whether the RAID level is equal toeach other or not. Alternatively, it is determined that the RAID levelis not set to at least one of those (Step 2014).

In the case where the RAID level is different from each other (theresult in Step 2014 is “no”), the processor 413 of the storagemanagement server 102 sets the storage tier having the higher-order RAIDlevel to be higher (Step 2016). The higher-order RAID level indicatesthe higher performance RAID level. For example, with respect to faulttolerance, the RAID1 is higher than the RAID5. Therefore, the RAID1 ishigher than the RAID5 in view of the fault tolerance. The informationfor determining whether the RAID level is higher or lower may be held inthe storage management server 102 in advance, or may be determined bythe administrator.

In the case where the RAID level is equal to each other or not set in atleast one of those (the result in Step 2014 is “no”), both of thestorage tiers are set to be the same (Step 2017).

Now, a description will be given in more detail of the operation of FIG.14 and FIG. 16 while comparing the storage tier Tier1 and the storagetier Tier2, and then the storage tier Tier2 with the storage tier Tier3with reference to FIG. 10.

First, when Tier1 and Tier2 are compared with each other, because Tier1is of high performance and Tier2 is of low performance, the device typeis different therebetween. Accordingly, the result of Step 2011 of FIG.16 is “no”, and Tier1 having the higher-order tier type is defined tohave the higher-order storage tier than Tier2 in Step 2013.

Then, when Tier2 and Tier3 are compared with each other, because thedevice types of Tier2 and Tier3 are equal to each other, the result inStep 2011 is “yes”. Then, the disk type is not set in Tier3.Accordingly, the result in Step 2012 is also “yes”.

Further, when of the RAID levels of Tier2 and Tier3 are compared witheach other, the RAID level of Tier2 is RAID1 and the RAID level of Tier3is RAID5. In this embodiment, because RAID5 is higher than RAID1, Tier2is higher than Tier3.

FIG. 17 and FIG. 18 are flowcharts showing an example of a procedure ofproducing the migration plan.

FIG. 17 is a flowchart showing an example of a procedure of producingthe migration plan according to the embodiment of this invention. Theprocedure shown in FIG. 17 is a process mainly in the case where theexecution of another migration plan is not overlapped with the executionscheduled time of the produced migration plan.

The processor 413 of the storage management server 102 executes the GUIprogram 433, to thereby display a screen that registers the migrationplan through the web browser 131 of the management client 103 (Step1511). The administrator sets the migration group that migrates data onthe displayed screen, the migration destination storage tier, and thedesignated end time.

Hereinafter, a description will be described of the operation of theadministrator in Step 1511 with reference to FIG. 19 showing the screenthat is displayed in the web browser 131 of the management client 103.

FIG. 19 shows a screen for registering the migration plan according tothe embodiment of this invention.

The administrator first operates a select field 2211 on the basis ofinformation on an MG ID 2212, a belonging VOL #2213, and a migrationdestination tier 2214 which are displayed on the screen, and selects onemigration group. The MG ID 2212, the belonging VOL #2213, and themigration destination tier 2214 correspond to the MG ID 811, thebelonging VOL #812, and the migration destination tier 813 in themigration group table 442, respectively.

Subsequently, the administrator operates a select field 2221 on thebasis of information on a tier name 2222, a capacity 2223, a device ID2224, a device type 2225, a RAID level 2226, and a disk type 2227, tothereby select the migration destination storage tier of the volumewithin the migration group. The tier name 2222, the capacity 2223, thedevice ID 2224, the device type 2225, the RAID level 2226, and the disktype 2227 correspond to the tier name 1012, the capacity 1014, thedevice ID 1015, the device type 1016, the RAID level 1017, and the disktype 1018 in the storage tier table 444, respectively.

In addition, the administrator inputs a designated end time 2231.Finally, in order to execute the selected contents, the manager operatesan execute button 2241. In the case where the selected contents arecanceled, the administrator operates a cancel button 2242.

Subsequently, the processor 413 of the storage management server 102executes the execution management program 435, to thereby searches thepriority table 447 for the subject priority on the basis of informationon the migration group designated by the administrator, and themigration destination storage tier (Step 1512).

The processor 413 of the storage management server 102 executes theexecution management program 435, to thereby calculate a period of timerequired for the data migration which is designated by theadministrator. In the calculation of the period of time required for thedata migration, for example, a sum of capacities of the volumes thatbelong to the migration group is calculated based on the configurationinformation of the volumes that belong to the migration group, and aproduct of the sum and the data transfer speed per unit capacity isobtained. The data transfer speed per unit capacity is held by thestorage management server 102 in advance. The configuration informationof the volume is acquired from the migration group table 442 and thevolume table 445.

Subsequently, the processor 413 of the storage management server 102sets a scheduled end time. The scheduled end time is a time obtained bysubtracting a constant time (hereinafter referred to as “margin time”)from the designated end time designated by the administrator. The margintime is held by the storage management server 102 in advance. Theprocessor 413 of the storage management server 102 sets a scheduledstart time on the basis of the scheduled end time and the requiredperiod of time (Step 1513).

The processor 413 of the storage management server 102 executes thetable management program 434, to thereby acquire the registeredmigration plan from the migration plan table 443. In addition, theprocessor 413 of the storage management server 102 acquires thescheduled start time and the scheduled end time (hereinafter, a periodof time between the scheduled start time and the scheduled end time willbe called “scheduled period of time”) of the acquired migration plan,and determines whether the scheduled period of time that is set in theprocess of Step 1513 is overlapped with the scheduled period of time ofanother migration plan, or not (Step 1514).

In the case where the scheduled period of time is not overlapped withthat of other migration plans (the result in Step 1514 is “no”), theprocessor 413 of the storage management server 102 executes theexecution management program 435, to thereby determine whether thescheduled start time is before the present time, or not (Step 1611).More specifically, the processor 413 compares the scheduled start timethat has been set in the process of Step 1512 with the present time.

In the case where the scheduled start time is before the present time(the result in Step 1611 is “no”), the processor 413 of the storagemanagement server 102 executes the table management program 434, tothereby register the information in the migration plan table 443 (Step1613). The information to be registered in the migration plan table 443is information set in the processes of Steps 1511 and 1512 andinformation designated by the administrator.

In the case where the scheduled start time is not before the presenttime (the result in Step 1611 is “yes”), the processor 413 of thestorage management server 102 executes the execution management program435, to thereby determine whether the scheduled end time is later thanthe designated end time, or not (Step 1612). More specifically, theprocessor 413 compares the scheduled end time set in the process of Step1512 with the designated end time designated by the administrator.

In the case where the scheduled end time is earlier than the designatedend time (the result in Step 1612 is “no”), the processor 413 of thestorage management server 102 executes the storage operation program431, to thereby instruct the data migration to the storage system 101(Step 1614). In this situation, the processor 413 of the storagemanagement server 102 designates the migration source volume and themigration destination volume which are described in the volume relationtable 446 from the migration plan to the storage system 101.

In the case where the scheduled end time is later than the designatedend time (the result in Step 1612 is “yes”), the processor 413 of thestorage management server 102 notifies the administrator of the error(Step 1615).

The above process is a process in the case where the execution ofanother migration plan is not overlapped with the execution scheduledtime of the produced migration plan. Hereinafter, a description will begiven of the process in the case where the execution of anothermigration plan is overlapped with the execution scheduled time of theproduced migration plan with reference to FIG. 18.

FIG. 18 is a flowchart showing an example of the procedure of producingthe migration plan according to the embodiment of this invention.Specifically, a case in which the execution of another migration plan isoverlapped with the execution scheduled time of the produced migrationplan is illustrated.

In the case where the scheduled period of time is overlapped with eachother (the result in Step 1514 of FIG. 17 is “yes”), the processor 413of the storage management server 102 executes the execution managementprogram 435, to thereby select the migration plan having a higherpriority (Step 1711). More specifically, the processor 413 compares thepriority of the overlapped migration plan with the priority set in theprocess of Step 1511. In this situation, in the case where thepriorities are equal to each other, the processor 413 selects theoverlapped migration plan.

Subsequently, the processor 413 of the storage management server 102executes the execution management program 435, to thereby determinewhether the migration plan that has been selected in the process of Step1711 is being executed, or not (Step 1712).

In the case where the migration plan is in execution (the result in Step1712 is “yes”), the processor 413 of the storage management server 102executes the execution management program 435, to thereby delay thescheduled start time of the migration plan not selected in the processof Step 1711 so that those executions are not overlapped with each other(Step 1715).

In the case where the migration plan selected in the process of Step1711 is not in execution (the result in Step 1712 is “no”), theprocessor 413 of the storage management server 102 executes theexecution management program 435, to thereby hasten the scheduled starttime of the migration plan selected in the process of Step 1711. Morespecifically, the processor 413 hastens the scheduled start time of themigration plan selected in the process of Step 1711 as much as theperiod of time between the scheduled start time and the present time, asmuch as the period of time between the scheduled end time and thepresent time, to the scheduled end time of another migration plan, or tothe latest time among the times corresponding to the periods of time,the scheduled end time, and the present time, on the basis of theinformation on the migration plan other than the migration plan comparedin the process of Step 1711 and the information on the present time(Step 1713).

The processor 413 of the storage management server 102 may not changethe scheduled start time according to the scheduled end time of anothermigration plan, but may execute the process of FIG. 18 with respect tothe migration plan selected in the process of Step 1711 and themigration plan whose scheduled end time competes against the scheduledend time thereof in this step.

Subsequently, the processor 413 of the storage management server 102executes the execution management program 435, to thereby compare thescheduled period of time changed in the process of Step 1713 with thescheduled period of time of another migration plan compared in theprocess of Step 1711, and determine whether the scheduled period of timeis overlapped with each other, or not (Step 1714).

In the case where the scheduled period of time is overlapped with eachother (the result in Step 1714 is “yes”), the processor 413 of thestorage management server 102 executes a process of Step 1715.

In the case where the scheduled period of time is not overlapped witheach other (the result in Step 1714 is “no”), the processor 413 of thestorage management server 102 executes the processes after Step 1611with respect to the respective migration groups whose scheduled periodof time has been changed.

Now, a process of producing the migration plan will be described withreference to an example of FIG. 20.

FIG. 20 is a diagram for explaining a specific example of a procedure ofproducing the migration plan according to the embodiment of thisinvention.

In the migration plan table before producing the migration plan, thereis registered a migration plan whose MG ID 911 is “101”.

The administrator executes the processes of Steps 1511 to 1513 toregister a migration plan whose designated end time is “December 1012:00”, the scheduled start time is “December 10 9:00”, the scheduledend time is “December 10 10:00”, and the priority is “5”, at the presenttime “December 10 9:00”. The MG ID of the migration plan is set to“102”, and the scheduled start time 913, the scheduled end time 914, andthe priority 912 are determined by the execution of the executionmanagement program 435.

Subsequently, the processor 413 of the storage management server 102determines whether the scheduled period of time of the migration planwhose MG ID is “101” is overlapped with the scheduled period of time ofthe migration plan whose MG ID is “102”, or not, through the process ofStep 1514.

The migration plan whose MG ID is “101” has the scheduled start time of“December 10 9:00” and the scheduled end time of “December 10 10:00”.The migration plan whose MG ID is “102” has the scheduled start time of“December 10 9:30”, and the scheduled end time of “December 10 10:00”.Thus, the scheduled periods of time of those migration plans areoverlapped with each other.

Accordingly, because the result of Step 1514 is “yes”, the processor 413of the storage management server 102 executes the process of Step 1711.In the process of Step 1711, the table management program 232 isexecuted, and the migration plan whose MG ID is “101” that is higher inthe priority is selected.

The processor 413 of the storage management server 102 determineswhether the migration plan having the MG ID of “101” is being executed,or not, through the process of Step 1712. Because the migration planhaving the MG ID of “101” is unprocessed, the processor 413 executes theprocess of Step 1713. As a result, the scheduled start time of themigration plan having the MG ID of “101” is hastened up to 9:00 which isthe present time. In this situation, the scheduled start time of themigration plan having the MG ID of “101” is “9:00”, and the scheduledend time thereof is “9:30”.

Subsequently, the processor 413 of the storage management server 102determines whether the scheduled periods of time of the migration planhaving the MG ID of “101” and that of the migration plan whose MG ID of“102” are overlapped with each other, or not, through a process of Step1714.

The processor 413 of the storage management server 102 executes aprocess of Step 1715 because the scheduled periods of time of themigration plan having the MG ID of “101” and that of the migration planwhose MG ID of “102” are overlapped with each other. The processor 413of the storage management server 102 changes the scheduled start timeand the scheduled end time of the migration plan having the MG ID of“102” to “9:30” and “10:30”, respectively, so as not to be overlappedwith the scheduled period of time of the migration plan having the MG IDof “101”.

In addition, the processor 413 of the storage management server 102executes the processes after Step 1611 of FIG. 17 with respect to themigration plans having the MG ID of “101” and the MG ID of “102”,respectively.

The processor 413 of the storage management server 102 executes theprocess of Step 1611 to determine whether the scheduled start time ofthe migration plan having the MG ID of “101” is before the present time,or not.

Because the scheduled start time of the migration plan having the MG IDof “101” is not before the present time, the processor 413 of thestorage management server 102 executes the process of Step 1612 todetermine whether the scheduled end time is before the designated endtime, or not. In addition, the processor 413 executes the process ofStep 1614, and executes the migration plan having the MG ID of “101”.

On the other hand, because the scheduled start time of the migrationplan having the MG ID of “102” is not before the present time, theprocessor 413 executes the process of Step 1613, and registers thescheduled start time and the scheduled end time in the migration plantable 443.

FIG. 21 is a flowchart showing a procedure of the volume migratingprocess registered in the migration plan according to the embodiment ofthis invention.

The processor 413 of the storage management server 102 executes thetable management program 434, to thereby regularly acquire the migrationplan table 443 (Step 1811).

The processor 413 of the storage management server 102 executes theexecution management program 435, to thereby retrieve the scheduledstart time of the migration plan acquired in the process of Step 1811,and determine whether the scheduled start time has passed, or not, andwhether the unprocessed migration plan exists, or not (Step 1812).

In the case where the scheduled start time has passed, and theunprocessed migration plan does not exist (the result in Step 1812 is“no”), the processor 413 of the storage management server 102 terminatesthis process.

In the case where the scheduled start time has passed, and theunprocessed migration plan exists (the result in Step 1812 is “yes”),the processor 413 of the storage management server 102 executes theexecution management program 425, to thereby determine whether themigration plan in execution exists, or not (Step 1813). Morespecifically, the processor 413 refers to the execution status of themigration plan acquired in the process of Step 1811 for determination.

In the case where the migration plan in execution does not exist (theresult in Step 1813 is “no”), the processor 413 of the storagemanagement server 102 executes the storage operation program 431, tothereby instruct the data migration to the storage system 101 (Step1814). In this situation, the processor 413 of the storage managementserver 102 designates the migration source volume and the migrationdestination volume, which are described in the volume relation table446, from the migration plan having the scheduled start time passed.

In the case where the migration plan in execution exists (the result in

Step 1813 is “yes”), the processor 413 of the storage management server102 executes the execution management program 435, to thereby comparethe priority of the migration plan in execution with the priority of themigration plan having the scheduled start time passed, and determinewhether the priority of the migration plan having the scheduled starttime passed is higher, or not (Step 1815).

In the case where the priority of the migration plan having thescheduled start time passed is higher (the result in Step 1815 is“yes”), the processor 413 of the storage management server 102 executesthe storage operation program 431, to thereby suspend the data migratingprocess of the migration plan in execution. Then, the processor 413designates the migration source volume and the migration destinationvolume, which are described in the volume relation table 446, from themigration plan having the scheduled start time passed, and instructs thedata migration to the storage system 101 (Step 1816). The stoppedprocess is again executed in a case where the migration plan that ishigher in priority does not execute.

FIG. 22 is an example of a flowchart that instructs the stop of the datamigrating process of the storage system 101 according to the embodimentof this invention. This process represents the stop of the datamigrating process in the process of Step 1816 shown in FIG. 18.

The processor 413 of the storage management server 102 executes thestorage operation program 431, to thereby access to the storage system101 and acquire the information on the process that stops (Step 1911).

The processor 413 of the storage management server 102 executes theexecution management program 435, to thereby determine whether theprocess in execution is the data migrating process, or the data deletingprocess (Step 1912).

In the case where the process in execution is the data deleting process(the result in Step 1912 is “no”), the processor 413 of the storagemanagement server 102 executes the storage operation program 431, tothereby acquire information on the subject storage device (Step 1914).In addition, the processor 413 of the storage management server 102determines whether the interruption of the data deleting process isenabled, or not (Step 1915).

The interruption of the process means that the subject process issuspended when the storage operation program 431 is executed to transmita stop command of the subject process to the storage system 101, and thesuspended process is restarted when the storage operation program 431 isexecuted to transmit the restart command of the subject process to thestorage system 101.

In the case where the process in execution is the data migrating process(the result in Step 1912 is “yes”), the processor 413 of the storagemanagement server 102 executes the storage operation program 431, tothereby acquire the information on the subject storage device (Step1913). In addition, the processor 413 of the storage management server102 determines whether the interruption of the data migrating process isenabled, or not (Step 1915).

In the case where the process in execution can be interrupted (theresult in Step 1915 is “yes”), the processor 413 of the storagemanagement server 102 executes the storage operation program 431, tothereby instruct the interruption of the present process to the storagesystem 101 (Step 1916).

In the case where the process in execution cannot be interrupted (theresult in Step 1915 is “no”), the processor 413 of the storagemanagement server 102 executes the storage operation program, to therebyinstruct the forced termination of the present process to the storagesystem 101 (Step 1917). Further, in the subject process, the processor413 updates the progress 1215 of the volume relation table 446. Forexample, when the value of the progress 1215 is “migrating”, theprocessor 413 changes the value to “unprocessed”, and when the value ofthe progress 1215 is “deleting”, the processor 413 changes the value to“migrating”.

The forced termination of the process means that the processor 413executes the storage operation program 431, thereby transmitting theforced termination command of the subject process to the storage system101 to cancel the subject process. In this situation, in order torestart the process, the processor 413 of the storage management server102 is required to execute the storage operation program 431 to againtransmit the execution command of the subject process. In thissituation, the subject process is executed from the beginning.

FIG. 23 is a diagram for explaining a specific example of a procedure ofexecuting the migration plan according to the embodiment of thisinvention.

In the migration plan table before execution shown in FIG. 23, themigration plan having the MG ID of “201” is “migrating”, and themigration plan having the MG ID of “202” is “unprocessed”.

A description will be given of a case in which the execution of themigration plan having the MG ID of “201” is not completed, and thescheduled start time of the migration plan having the MG ID of “202” haspassed (in the case where the result of Step 1812 is “yes”).

In this case, because the migration plan having the MG ID of “201” is inexecution, the processor 413 executes the process of Step 1815 tocompare the priority of the migration plan having the MG ID of “201”with the priority of the migration plan having the MG ID of “202”. As aresult, because the priority of the migration plan having the MG ID of“202” is higher, the migration plan having the MG ID of “201” issuspended, and the migration plan having the MG ID of “202” is executed.In this situation, the migration plan table 443 is in a state of themigration plan table after execution shown in FIG. 23.

According to the embodiment of this invention, it is possible to startthe volume migration that is higher in priority such that the processcompletes before the end time. Therefore, the migrating process of thevolume that is higher in priority can be completed by the designatedtime.

Also, according to the embodiment of this invention, in the case where atiming at which the access frequency is increased is grasped by a systemmonitor and the like in advance, it is possible to complete themigrating process of the volume before the processing performance isdeteriorated due to increased access frequency.

In the embodiment of this invention, the data migration is executed bythe virtualization device 107 in a state where a plurality of storagedevices are logically identified as one storage device. Now, adescription will be given of a modified example in which the datamigration is conducted in the interior of one storage system.

More specifically, the modified example is different from the computerio system 100 shown in FIG. 1 in that the virtualization device 107 isnot included, and the storage management server 102 manages one storagesystem 101. Other structures are the same as those in FIG. 1.

The processor 413 of the storage management server 102 executes thestorage operation program 431, to thereby transmit instructions of thedata migrating process and the data deleting process to the storagesystem 101.

According to the modified example of the embodiment of this invention,it is possible to apply this invention to the configuration in which onestorage system 101 is disposed for the storage management server 102.Accordingly, even in a computer system that is relatively small-scaled,it is possible to complete the migrating process of the volume beforethe access frequency increases, by means of the system monitor.

While the present invention has been described in detail and pictoriallyin the accompanying drawings, the present invention is not limited tosuch detail but covers various obvious modifications and equivalentarrangements, which fall within the purview of the appended claims.

1. A computer system, comprising: a storage system; a host computer thatis coupled to the storage system via a network; and a storage managementserver that can access to the storage system and the host computer,wherein the storage system comprises a first interface that is coupledto the network, a first processor that is coupled to the firstinterface, a first memory that is coupled to the first processor, and astorage device that stores data that is read or written by the hostcomputer, and provides at least one storage area of the storage devicefor the host computer as at least one volume, wherein the storagemanagement server comprises a second interface that is coupled to thestorage system, a second processor that is coupled to the secondinterface, and a second memory that is coupled to the second processor,wherein the second memory stores configuration information of the volumeand configuration information of a volume migration group, and whereinthe second processor executes a volume migrating process for migratingdata stored in the volume to another volume with respect to themigration group, in which the second processor: calculates a requiredperiod of time for migrating the data based on a size of data to bemigrated, volume configuration information of a first volume included ina first migration group in which the data to be migrated is stored, andvolume configuration information of a second volume included in a secondmigration group to which the data is migrated, generates a volumemigration plan with respect to the migration group by determining astart time at which the data migration starts based on the calculatedrequired period of time and an input end time, sets a priority of thegenerated volume migration plan of the migration group, and changes, ina case where a period of time during which the produced volume migrationplan is executed and a period of time during which an existing volumemigration plan is executed are overlapped with each other, based on aresult of comparing a priority of the generated volume migration planwith a priority of the existing volume migration plan, the start time ofat least one of the generated volume migration plan and the existingvolume migration plan, in accordance with the priority of the volumemigration plan which has a higher priority of the generated volumemigration plan and the existing volume migration plan.
 2. The computersystem according to claim 1, wherein the second processor hastens astart time of the volume migration plan having a higher priority.
 3. Thecomputer system according to claim 1, wherein the second processordelays a start time of a volume migration plan having a lower priority.4. The computer system according to claim 1, wherein the second memorystores configuration information of the storage system, and wherein thepriority is determined based on at least one of the volume configurationinformation of the first volume and the second volume, and theconfiguration information of the storage system which provides the firstvolume and the second volume.
 5. The computer system according to claim1, wherein the volume migrating process further comprises: instructingthe storage system a first process of writing the data stored in thefirst volume into the second volume; and instructing the storage systema second process of deleting the data stored in the first volume afterthe completion of the first process, wherein the priority is set in thefirst process and the second process, individually.
 6. The computersystem according to claim 1, wherein the storage system executes, inaccordance with an instruction sent from the storage management server,a data writing process of writing the data stored in the source volumeinto the destination volume and a data deleting process of deleting thedata stored in the source volume, and wherein the second processorcompares, in a case where a first volume migration plan in which atleast one of the data writing process and the data deleting process isbeing executed and a second volume migration plan in which any of thedata writing process and the data deleting process is not executed areregistered, when a start time of the second volume migrating plan comesduring processing of the first volume migrating plan, a priority of thefirst volume migration plan with a priority of the second volumemigration plan to execute the volume migration plan having a higherpriority.
 7. The computer system according to claim 6, wherein thesecond processor suspends, in a case where the priority of the firstvolume migration plan is lower than the priority of the second volumemigration plan, the processing of the first volume migration plan, andexecutes the second volume migration plan.
 8. The computer systemaccording to claim 1, wherein the second processor generates displaydata of a screen on which selection of the first volume, selection ofthe second volume, and the end time of the process of migrating the datafrom the selected first volume to the selected second volume are input,and generates the volume migration plan based on the selected firstvolume, the selected second volume, and the input end time.
 9. Thecomputer system according to claim 1, wherein the second processor:generates display data of a screen on which selection of the firstvolume, selection of the second volume, and the end time of the processof migrating the data from the selected first volume to the selectedsecond volume are input, calculates scheduled end time by subtracting apredetermined margin time from the input end time, and generates thevolume migration plan based on the selected first volume, the selectedsecond volume, and the scheduled end time.
 10. A storage managementserver that is coupled to a storage system having a storage device thatstores data therein, the storage management server comprising: aninterface coupled to the storage system; a processor coupled to theinterface; and a memory coupled to the second processor, wherein thestorage system provides at least one storage area of the storage devicefor a host computer as at least one volume, wherein the memory storesconfiguration information of the volume and configuration information ofa volume migration group, wherein the processor executes a volumemigrating process for migrating data stored in the volume to anothervolume with respect to the migration group, in which the processor:calculates a required period of time for migrating the data based on asize of data to be migrated, volume configuration information of a firstvolume included in a first migration group in which the data to bemigrated is stored, and volume configuration information of a secondvolume included in a second migration group to which the data ismigrated, generates a volume migration plan with respect to themigration group by determining a start time at which the data migrationstarts based on the calculated required period of time and an input endtime, sets a priority of the generated volume migration plan of themigration group, and changes, in a case where a period of time duringwhich the produced volume migration plan is executed and a period oftime during which an existing volume migration plan is executed areoverlapped with each other, based on a result of comparing a priority ofthe generated volume migration plan with a priority of the existingvolume migration plan, the start time of at least one of the generatedvolume migration plan and the existing volume migration plan, inaccordance with the priority of the volume migration plan which has ahigher priority of the generated volume migration plan and the existingvolume migration plan.
 11. The storage management server according toclaim 10, wherein the processor hastens a start time of the volumemigration plan having a higher priority.
 12. The storage managementserver according to 10, wherein the processor delays a start time of avolume migration plan having a lower priority.
 13. The storagemanagement server according to claim 10, wherein the second memorystores configuration information of the storage system, and wherein thepriority is determined based on at least one of the volume configurationinformation of the first volume and the second volume, and theconfiguration information of the storage system which provides the firstvolume and the second volume.
 14. The storage management serveraccording to claim 10, wherein the volume migrating process furthercomprises: a first process of writing the data stored in the firstvolume into the second volume; and a second process of deleting the datastored in the first volume after the completion of the first process,and wherein the priority is set in the first process and the secondprocess, individually.
 15. The storage management server according toclaim 10, wherein the volume migrating process further comprises a datawriting process of writing the data stored in the source volume into thedestination volume and a data deleting process of deleting the datastored in the source volume, and wherein the processor compares, in acase where a first volume migration plan in which at least one of thedata writing process and the data deleting process is being executed anda second volume migration plan in which the volume migrating process isnot executed are registered, when a start time of the second volumemigrating plan comes during processing of the first volume migratingplan, a priority of the first volume migration plan with a priority ofthe second volume migration plan to execute the volume migration planhaving a higher priority.
 16. The storage management server according toclaim 15, wherein the processor suspends, in a case where the priorityof the first volume migration plan is lower than the priority of thesecond volume migration plan, the processing of the first volumemigration plan, and executes the second volume migration plan.
 17. Thestorage management server according to claim 10, wherein the processor:generates display data of a screen on which selection of the firstvolume, selection of the second volume, and the end time of the processof migrating the data from the selected first volume to the selectedsecond volume are input, and generates the volume migration plan basedon the selected first volume, the selected second volume, and the inputend time.
 18. The storage management server according to claim 10,wherein the processor: generates display data of a screen on whichselection of the first volume, selection of the second volume, and theend time of the process of migrating the data from the selected firstvolume to the selected second volume are input, calculates scheduled endtime by subtracting a predetermined margin time from the input end time,and generates the volume migration plan based on the selected firstvolume, the selected second volume, and the scheduled end time.
 19. Adata migrating method in a computer system including a storage system, ahost computer that is coupled to the storage system via a network, and astorage management server that can access to the storage system and thehost computer, wherein the storage system comprises a first interfacethat is coupled to the network, a first processor that is coupled to thefirst interface, a first memory that is coupled to the first processor,and a storage device that stores data that is read or written by thehost computer, and provides at least one storage area of the storagedevice for the host computer as at least one volume, wherein the storagemanagement server comprises a second interface that is coupled to thestorage system, a second processor that is coupled to the secondinterface, and a second memory that is coupled to the second processor,and wherein the second memory stores configuration information of thevolume and configuration information of a volume migration group, thedata migrating method comprising the steps of: calculating, by thesecond processor, a required period of time for migrating the data basedon a size of data to be migrated, volume configuration information of afirst volume included in a first migration group in which the data to bemigrated is stored, and volume configuration information of a secondvolume included in a second migration group to which the data ismigrated; generating a volume migration plan with respect to themigration group by determining, by the second processor, a start time atwhich the data migration starts based on the calculated required periodof time and an input end time; setting, by the second processor, apriority of the generated volume migration plan of the migration group;and changing, by the second processor, in a case where a period of timeduring which the produced volume migration plan is executed and a periodof time during which an existing volume migration plan is executed areoverlapped with each other, based on a result of comparing a priority ofthe generated volume migration plan with a priority of the existingvolume migration plan, the start time of at least one of the generatedvolume migration plan and the existing volume migration plan, priorityof the volume migration plan which has a higher priority of thegenerated volume migration plan and the existing volume migration plan.